fix(release): publish to PyPI by correcting semantic-release output name#82
Merged
Merged
Conversation
The "Publish to PyPI" step was gated on ``steps.release.outputs.new-release-published``, but cycjimmy/semantic-release-action exposes its outputs with underscores (``new_release_published``). The hyphenated reference was always empty, so the step was silently skipped on every release — which is why the 0.11.x and 0.12.x series never reached PyPI (latest published there is 0.10.3) while the GitHub Releases carried the wheels. Use the correct ``new_release_published`` output so a released version is actually uploaded to PyPI. This `fix:` commit itself cuts the next patch (0.12.4), which the corrected workflow will publish — restoring PyPI as a resolvable source for downstreams that pin recent spotoptim (e.g. spotforecast2 >= 0.12.3). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
spotoptim's
release.ymlgates the Publish to PyPI step onsteps.release.outputs.new-release-published, butcycjimmy/semantic-release-action@v4exposes its outputs with underscores(
new_release_published). The hyphenated reference is always empty, so the stephas been silently skipped on every release — which is why the 0.11.x/0.12.x
series never reached PyPI (latest there is
0.10.3) even though the GitHubReleases carried the built wheels.
Fix
Reference the correct
new_release_publishedoutput. Thisfix:commit itselfcuts the next patch (0.12.4), and the corrected workflow will publish it to
PyPI — restoring PyPI as a resolvable source for downstreams that pin recent
spotoptim (e.g.
spotforecast2 >= 0.12.3).0.12.4 includes the steady-state
inverse_transformfix already merged in0.12.3 (#81), so a single PyPI publish unblocks parallel SpotOptim tuning
end-to-end.
🤖 Generated with Claude Code